home *** CD-ROM | disk | FTP | other *** search
- STDUMP(1) Last changed: 1-4-99
-
-
- NNAAMMEE
- ssttdduummpp - Dumps a file of intermediate-code debugging information
-
- SSYYNNOOPPSSIISS
- ssttdduummpp [--aa] [--bb] [--cc] [--gg] [--hh] [--ii] [--nn _n_u_m_b_e_r] _f_i_l_e
-
- IIMMPPLLEEMMEENNTTAATTIIOONN
- IRIX systems
-
- DDEESSCCRRIIPPTTIIOONN
- When compiling for the old 32-bit ABI (--3322), the compilers generate an
- intermediate language which is separated into binary instructions and
- debugging information, each constituting a separate file. Use ssttdduummpp
- to dump a file containing debugging information which was generated by
- the compilers. ssttdduummpp writes to the standard output. The
- organization of the output is simple but the details of the output are
- complicated. The detailed output is be defined here. The output of
- ssttdduummpp is subject to change and one should not rely on the output
- format remaining the same from release to release.
-
- The organization of the output is that for each source file
- represented in _f_i_l_e, there may be auxiliary-symbols, local-symbols, a
- file-indirect-table, optimization-entries, procedures, and line-
- numbers. There is only one externals-table and one dense-number-table
- in _f_i_l_e.
-
- By default, ssttdduummpp prints all information about all sections of the
- debugging information. The options (described on this man page)
- restrict the output to the selected sections.
-
- The _f_i_l_e may be an object file (such as produced by cccc --cc), an
- executable file (such as produced by lldd(1) or cccc(1)), or a debugging
- information file (which may be produced as described below).
-
- Normally, debugging information files (and instruction files) are
- placed in //ttmmpp and removed after each compilation. Use the --kkeeeepp
- option to cccc, or ff7777(1), to force the compiler to preserve these files
- in the target directory. When this switch is used, the compilation of
- ffiillee.._x (where _x is c for C or f for FORTRAN, for example) will produce
- the intermediate files ffiillee.._B (instructions) and ffiillee.._T (debugging
- information). The latter file (ffiillee.._T)) mmaayy bbee uusseedd aass iinnppuutt ttoo
- ssttdduummpp..
-
- ssttdduummpp accepts the following options:
-
- --aa Print the dense number table. This section is empty for
- object and executable files.
-
- --bb Print the externals table.
-
- --cc Print the local debugging symbols. The source file name is
- printed here.
-
- --gg Print the auxiliaries table. This table has encoded in it in
- a complex way the actual data types of all the data in the
- symbols. The local-symbol and externals table sections show
- this data expanded into semi-readable text.
-
- --hh Print the line table. One source line number per 32-bits of
- executable code.
-
- --ii Print the File Indirect Table.
-
- --nn _n_u_m_b_e_r
- Print information about only the source file whose number is
- specified. Files are numbered sequentially starting with
- zero.
-
- FFIILLEESS
- //ttmmpp//ccttmmssttaa_x_x_x_x_x Default name of debugging information file for
- process id _x_x_x_x_x
-
- _f_i_l_e..TT Name of debugging information file created by the
- --kkeeeepp option
-
- //uussrr//bbiinn//ssttdduummpp Debugging information dump program
-
- SSEEEE AALLSSOO
- eellffdduummpp(1), ddwwaarrffdduummpp(1), cccc(1), ff7777(1), ppcc(1), aabbii((55))
-
- NNOOTTEESS
- Do not use ssttdduummpp to display the debugging information of 64-bit (--6644)
- or new 32-bit ABI (--nn3322) object files. Use the ddwwaarrffdduummpp(1) command
- instead.
-
- To see the linking information, specify eellffdduummpp(1) instead of ssttdduummpp.
-
- This man page is available only online.
-
-